Systems and methods for querying fleet information stored in a distributed data center

ABSTRACT

This disclosure relates to a distributed data center that includes resources carried by a fleet of vehicles. Individual vehicles carry sensors configured to generate output signals conveying information related to the vehicles and/or the surroundings of the vehicles. The system includes a remote computing server configured to obtain executable code from a user, and subsequently transmit the executable code to individual vehicles in the fleet. Individual vehicles locally execute the executable code to produce local results, and subsequently transfer the results to the remote computing server for presentation to the user.

FIELD

The systems and methods disclosed herein are related to using on-boardresources of individual vehicles in a fleet of vehicles as a distributeddata center that can be queried from a centralized server. Inparticular, a user can provide executable code through the centralizedserver for execution on individual vehicles of the fleet of vehicles.

BACKGROUND

Systems configured to record, store, and transmit video, audio, andsensor data associated with a vehicle, e.g. responsive to an accidentinvolving the vehicle, are known. Typically, such systems detect anaccident based on data from a single sensor such as an accelerometer.Some systems store information locally for subsequent analysis. VehicleEngine Control Component (ECM) systems are known. Such systemsinterface/interoperate with external computers (e.g., at an automobilemechanic) where the data stored by the ECM system is analyzed.

SUMMARY

One aspect of the disclosure relates to a system configured to use adistributed data center to query a fleet of vehicles. Thedata-processing resources carried by the fleet of vehicles operate asthe distributed data center. The fleet of vehicles may include one ormore of a first vehicle, a second vehicle, a third vehicle, and/or afourth vehicle, and so forth. Individual vehicles may include a set ofresources for data processing and/or electronic storage, including butnot limited to persistent storage. Individual vehicles may include a setof sensors configured to generate output signals conveying informationrelated to one or both of the operation of the individual vehicles andthe surroundings of individual vehicles. As used herein, transmissionand/or distribution of information may be considered a data processingfunction. As used herein, the terms data and information may be usedinterchangeably. The system may include sets of resources, sets ofsensors, a remote computing server (also referred to as centralizedserver), and/or other components.

One or more components of the system may include one or more processorsand/or other mechanisms/components for processing information. Forexample, a set of resources included in and/or carried by an individualvehicle may include one or more processors. For example, the remotecomputing server may include one or more processors. In someimplementations, other vehicle-specific components, such as, by way ofnon-limiting example, a vehicle event recorder, may include one or moreprocessors. In some implementations, some or all of the processors maybe configured via machine-readable instructions to perform variousfunctions. As used herein, the term “processor” is used interchangeablywith the term “physical processor.”

A set of resources included in and/or carried by an individual vehiclemay include one or more processors, electronic storage, a transceiver,and/or other components. The first vehicle may carry a first set ofresources. The second vehicle may carry a second set of resources, andso forth. The first set of resources may include a first transceiver.The second set of resources may include a second transceiver, and soforth.

Transceivers may be configured to transfer and/or receive information toand/or from other elements of the system, including but not limited toother vehicles (or components carried by other vehicles), the remotecomputing server, and/or other components. In some implementations,transceivers may be configured to transfer and/or receive informationwirelessly, and/or otherwise provide resources for the distribution ofinformation. For example, a transceiver may be configured to receiveexecutable code, queries, and/or other information. For example, atransceiver may be configured to transmit results from executable code,responses to queries, and/or other information, e.g., to a remotecomputing server. In some implementations, transceivers may beconfigured to obtain, measure, and/or otherwise determine one or moreconditions related to data transmissions. For example, one or morecurrent local data transmission conditions may include a currentbandwidth (e.g., in MB/s), a current transmission protocol (e.g., LTE,3G, 4G, 5G, Wi-Fi, etc.), a current transmission cost (e.g., in $/MB),and/or other conditions.

A set of sensors may be configured to generate output signals conveyinginformation. In some implementations, the generated information may berelated to one or both of the operation of one or more vehicles and thesurroundings of one or more vehicles. An individual set of sensors maybe carried by an individual vehicle. The generated information mayinclude timing information, location information, (vehicle) operatorinformation, and/or other information. In some implementations,generated information may be associated with timing information (e.g.,from a timer), location information, operator information, and/or otherinformation.

In some implementations, timing information may associate and/orotherwise relate the generated output signals with one or more momentsof generation by one or more particular sensors. For example, timinginformation may include time stamps that indicate moments of generation.For example, at a time labeled t₁ the speed of a vehicle may be 50 mph,at a time labeled t₂ the speed may be 55 mph, and so forth. A set oftime stamps or moments in time may form a timeline. In someimplementations, location information may associate and/or otherwiserelate the generated output signals with one or more locations ofgeneration (or, locations at the moment of generation) by one or moreparticular sensors. In some implementations, the operator informationmay associate and/or otherwise relate the generated output signals withindividual vehicle operators at the moments of generation. For example,a particular sensor may generate a particular output signal conveying aparticular operating parameter of an individual vehicle, such as speedand/or another operating parameter. The particular output signal mayinclude and/or be associated with a timestamp (e.g., time=t_(x)) thatindicates when the particular output signal was generated. For example,a series of output signals may be associated with a corresponding seriesof timestamps. In some implementations, the particular output signal maybe associated with a particular vehicle operator. For example, theparticular output signal may be associated with the particular vehicleoperator that was operating the individual vehicle at the time theparticular output signal was generated. In some implementations, a setof resources may be configured to store generated information, timinginformation, location information, operator information, and/or otherinformation, e.g. in electronic storage.

In some implementations, a sensor may be configured to generate outputsignals conveying information related to the operation of the vehicle(which may include information related to one or more operatingconditions of the vehicle). Information related to the operation of thevehicle may include feedback information from one or more of themechanical systems of the vehicle, and/or other information. In someimplementations, at least one of the sensors may be a vehicle systemsensor included in an engine control module (ECM) system or anelectronic control module (ECM) system of the vehicle. In someimplementations, one or more sensors may be carried by the vehicle. Thesensors of a particular vehicle may be referred to as a set of sensors.An individual sensor may be vehicle-specific.

Individual sensors may be configured to generate output signalsconveying information, e.g., vehicle-specific information. Theinformation may include visual information, motion-related information,position-related information, biometric information, and/or otherinformation. In some implementations, one or more components of thesystem may determine one or more parameters that are measured, derived,estimated, approximated, and/or otherwise determined based on one ormore output signals generated by one or more sensors.

Sensors may include, by way of non-limiting example, one or more of analtimeter (e.g. a sonic altimeter, a radar altimeter, and/or other typesof altimeters), a barometer, a magnetometer, a pressure sensor (e.g. astatic pressure sensor, a dynamic pressure sensor, a pitot sensor,etc.), a thermometer, an accelerometer, a gyroscope, an inertialmeasurement sensor, global positioning system sensors, a tilt sensor, amotion sensor, a vibration sensor, an image sensor, a camera, a depthsensor, a distancing sensor, an ultrasonic sensor, an infrared sensor, alight sensor, a microphone, an air speed sensor, a ground speed sensor,an altitude sensor, medical sensors (including but not limited to bloodpressure sensor, pulse oximeter, heart rate sensor, etc.),degree-of-freedom sensors (e.g. 6-DOF and/or 9-DOF sensors), a cornpass, and/or other sensors. As used herein, the term “motion sensor” mayinclude one or more sensors configured to generate output conveyinginformation related to position, location, distance, motion, movement,acceleration, and/or other motion-based parameters. Output signalsgenerated by individual sensors (and/or information based thereon) maybe stored and/or transferred in electronic files. In someimplementations, output signals generated by individual sensors (and/orinformation based thereon) may be streamed to one or more othercomponents of the system.

As mentioned, individual sensors may include image sensors, cameras,and/or other sensors. As used herein, the terms “camera” and/or “imagesensor” may include any device that captures images, including but notlimited to a single lens-based camera, a camera array, a solid-statecamera, a mechanical camera, a digital camera, an image sensor, a depthsensor, a remote sensor, a lidar, an infrared sensor, a (monochrome)complementary metal-oxide-semiconductor (CMOS) sensor, an active pixelsensor, and/or other sensors. Individual sensors may be configured tocapture information, including but not limited to visual information,video information, audio information, geolocation information,orientation and/or motion information, depth information, and/or otherinformation. Information captured by one or more sensors may be marked,timestamped, annotated, and/or otherwise processed such that informationcaptured by other sensors can be synchronized, aligned, annotated,and/or otherwise associated therewith. For example, video informationcaptured by an image sensor may be synchronized with informationcaptured by an accelerometer, GPS unit, or other sensor. Output signalsgenerated by individual image sensors (and/or information based thereon)may be stored and/or transferred in electronic files.

In some implementations, an image sensor may be integrated withelectronic storage such that captured information may be stored, atleast initially, in the integrated embedded storage of a particularvehicle. In some implementations, one or more components carried by anindividual vehicle may include one or more cameras. For example, acamera may include one or more image sensors and electronic storagemedia. In some implementations, an image sensor may be configured totransfer captured information to one or more components of the system,including but not limited to remote electronic storage media, e.g.through “the cloud.”

The system may be coupled to individual vehicles. For example, thesystem may be communicatively coupled to individual vehicles and/or tocomponents carried by individual vehicles, including but not limited totransceivers. For example, components of the system may be configured tocommunicate through one or more networks. The one or more networks may,by way of non-limiting example, include the internet.

The remote computing server may include one or more processors. Theremote computing server may be remote, separate, and/or discrete fromthe fleet of vehicles. The one or more processors may be configured viamachine-readable instructions to perform various functions. The remotecomputing server may be configured to facilitate presentation of a userinterface to a user of the remote computing server, including but notlimited to a third party using the remote computing server to query thefleet of vehicles. As used herein, the term “third party” may refer toan entity that neither owns nor operates the fleet of vehicles andneither owns nor operates the remote computing server. The userinterface may be configured to facilitate interaction between one ormore users and the remote computing server. For example, the userinterface may be configured to receive user input, executable code,and/or other information from a user. The remote computing server may befurther configured to transmit information based on received user input,received executable code, and/or other received information to somevehicles in the fleet or to all vehicles of the fleet. Information fromindividual vehicles, including but not limited to responses, resultsand/or other information generated by individual vehicles, may betransferred to, received by, and processed, analyzed, and/or presentedby the remote computing server.

In some implementations, a set of resources included in and/or carriedby an individual vehicle may include an event recorder (also referred toas vehicle event recorder). An event recorder may be configured togenerate, detect, identify, capture, and/or record information relatedto the operation of a vehicle. Information related to a vehicle mayinclude, by way of non-limiting example, information related to and/orbased on vehicle events. An event recorder may be configured to off-loadand/or otherwise transmit information. In some implementations, an eventrecorder may include one or more physical processors, electronicstorage, and/or other components. In some implementations, an eventrecorder may detect vehicle events based on a comparison of theinformation conveyed by the output signals from one or more sensors topredetermined (variable and/or fixed) values, threshold, functions,and/or other information. An event recorder may identify vehicle eventsand/or other information related to the operation of a vehicle inreal-time or near real-time during operation of a vehicle. In someimplementations, an event recorder may identify vehicle events and/orother information related to the operation of a vehicle based onpreviously stored information. For example, the previously storedinformation may be based on output signals generated days, weeks, monthsor more ago.

As used herein, the term “vehicle event” may refer to forward motion,motion in reverse, making a turn, speeding, unsafe driving speed,collisions, near-collisions, driving in a parking lot or garage, beingstalled at a traffic light, loading and/or unloading of a vehicle,transferring gasoline to or from the vehicle, and/or other vehicleevents in addition to driving maneuvers such as swerving, a U-turn,freewheeling, over-revving, lane-departure, short following distance,imminent collision, unsafe turning that approaches rollover and/orvehicle stability limits, hard braking, rapid acceleration, idling,driving outside a geo-fence boundary, crossing double-yellow lines,passing on single-lane roads, a certain number of lane changes within acertain amount of time or distance, fast lane change, cutting off othervehicles during lane-change speeding, running a red light, running astop sign, parking a vehicle, performing fuel-inefficient maneuvers,and/or other driving maneuvers or combinations thereof. Some types ofvehicle events may be based on the actions or motion of the vehicleitself. Other types of vehicle events may be based on the actions takenor performed by a vehicle operator. Some types of vehicle events may bebased on a combination of both the actions or motion of the vehicleitself and the actions taken or performed by a vehicle operator. Forexample, a particular vehicle event may include hard braking followed(within a predetermine window of time) by a sharp turn and/or swerve.This particular vehicle event may indicate a near-collision that wassevere enough that the vehicle operator decided that merely braking hardwould not be sufficient to avoid the collision. Another example of avehicle event that includes a combination of actions may be a lanechange followed (within a predetermine window of time) by hard braking,which may indicate a poor decision to initiate the lane change.

The one or more processors of the remote computing server and/or ofindividual sets of resources may be configured to execute one or morecomputer program components. The computer program components may includeone or more of a presentation component, an interface component, adistribution component, a code component, a local result component, acentralized result component, a parameter determination component, adetection component, a storage component, a monetization component,and/or other components.

The presentation component may be configured to facilitate presentationof user interfaces, reports, and/or results to users, third parties,and/or vehicle operators. In some implementations, the presentationcomponent may facilitate presentation of a user interface to a user ofthe remote computing server. In some implementations, the presentationcomponent may facilitate presentation of one or more user interfaces toone or more vehicle operators. In some implementations, the presentationcomponent may facilitate presentation of one or more reports, results,and/or user interfaces to a third party.

The interface component may be configured to facilitate interaction withusers. For example, the interface component may facilitate interactionthrough user interfaces. For example, the interface component mayreceive user input through a user interface. In some implementations,the interface component may receive user input from the user of a remotecomputing server. In some implementations, the interface component mayreceive user input from vehicle operators. In some implementations, theinterface component may receive user input from a third party.

The distribution component may be configured to transmit informationfrom the remote computing server to all or part of a fleet of vehicles.In some implementations, the distribution component may be configured totransmit information from the remote computing server to all or part ofthe transceivers that are included in and/or carried by a fleet ofvehicles. In some implementations, transmission may be wireless. In someimplementations, transmission may be point-to-point. In someimplementations, transmission may be broadcast. In some implementations,transmission may be bi-directional. For example, the distributioncomponent may be configured to transmit queries and/or executable codefrom the remote computing server to individual vehicles in a fleet,e.g., based on the current locations of the individual vehicles. Forexample, individual transceivers may be configured to receive queriesand/or executable code transmitted by the distribution component. Insome implementations, the presentation component, interface component,and/or one or more other components of the system may be configured todetermine and/or present one or both of warnings and/or recommendationsto a vehicle operator.

The code component may be configured to obtain executable code from auser, a third party, and/or from a source external to the system. Insome implementations, executable code may represent a query and/or analgorithm. In some implementations, executable code may include one ormore function calls to a standardized Application Program Interface orAPI. The one or more function calls may be associated with functionsthat operate on information related to vehicles, including but notlimited to the operation of vehicles and/or the surroundings ofvehicles. In some implementations, the standardized API may includedifferent subsets (e.g., different subsets of functions). The system maybe configured to control access by executable code to one or moreparticular subsets of the standardized API. For example, a first subsetof functions of the standardized API may be accessible to the executablecode of a particular third party, and a second subset of functions ofthe standardized API may be inaccessible to the executable code of theparticular third party, at the same time. For example, the first subsetand the second subset may be mutually exclusive. In someimplementations, the executable code may include definitions and/oralgorithms for particular vehicle events, particular maneuvers ofvehicles, particular conditions of vehicle operators, and/or otherinformation.

The local result component may be configured to execute executable codelocally on one or more individual vehicles. For example, the localresult component may be configured to execute executable code to producea result. Additionally, the set of resources on an individual vehiclemay be configured to transmit produced results to the remote computingserver.

The centralized result component may be configured to receive,aggregate, and/or otherwise process one or more results received fromindividual vehicles, including but not limited to results producedlocally by local result components of individual vehicles. In someimplementations, the centralized result component may be located at theremote computing server.

The parameter determination component may be configured to determinecurrent operating conditions and/or vehicle parameters. The parameterdetermination component may determine current operating conditionsand/or vehicle parameters based on the information conveyed by theoutput signals from the sensors and/or other information. The one ormore current operating conditions may be related to the vehicle, theoperation of the vehicle, physical characteristics of the vehicle,and/or other information. In some implementations, the parameterdetermination component may be configured to determine one or more ofthe current operating conditions one or more times in an ongoing mannerduring operation of the vehicle. In some implementations, the parameterdetermination component may be configured to determine one or more ofthe parameters one or more times in an ongoing manner during operationof the vehicle.

The detection component may be configured to detect vehicle events. Insome implementations, vehicle events may be related to current operatingconditions of a vehicle. In some implementations, vehicle events may berelated to the surroundings of a vehicle. In some implementations,vehicle events may be related to the operator of a vehicle. For example,a vehicle event may be based on comparing one or more vehicle parameterswith one or more thresholds.

The storage component may be configured to store information inelectronic storage. For example, the information may be stored in theelectronic storage of a particular vehicle. In some implementations, thestored information may be related to detected vehicle events, determinedvehicle parameters, executable code, and/or other information. In someimplementations, the storage component may be configured to storevehicle event records of detected vehicle events in electronic storage.

The monetization component may be configured to exchange access byexecutable code to at least a part of the fleet for compensation. Forexample, the results from running executable code may be provided to theuser and/or the third party in exchange for compensation.

In some implementations, one or more components of the system may beconfigured to obtain, receive, and/or determine contextual informationrelated to environmental conditions near and/or around vehicles.Environmental conditions may be related to weather conditions, trafficconditions, visibility, and/or other environmental conditions. In someimplementations, one or more environmental conditions may be receivedfrom one or more sources external to the vehicle. For example, a sourceexternal to the vehicle may include an external provider.

In some implementations, detection of vehicle events may further bebased one or more types of contextual information. In someimplementations, detection may be accomplished and/or performed at thevehicle.

As used herein, any association (or relation, or reflection, orindication, or correspondency) involving vehicles, sensors, vehicleevents, operating conditions, parameters, thresholds, functions,notifications, discrepancies, location-specific features, and/or anotherentity or object that interacts with any part of the system and/or playsa part in the operation of the system, may be a one-to-one association,a one-to-many association, a many-to-one association, and/or amany-to-many association or N-to-M association (note that N and M may bedifferent numbers greater than 1).

As used herein, the term “obtain” (and derivatives thereof) may includeactive and/or passive retrieval, determination, derivation, transfer,upload, download, submission, and/or exchange of information, and/or anycombination thereof. As used herein, the term “effectuate” (andderivatives thereof) may include active and/or passive causation of anyeffect. As used herein, the term “determine” (and derivatives thereof)may include measure, calculate, compute, estimate, approximate,generate, and/or otherwise derive, and/or any combination thereof.

These and other objects, features, and characteristics of the servers,systems, and/or methods disclosed herein, as well as the methods ofoperation and functions of the related elements of structure and thecombination of parts and economies of manufacture, will become moreapparent upon consideration of the following description and theappended claims with reference to the accompanying drawings, all ofwhich form a part of this disclosure, wherein like reference numeralsdesignate corresponding parts in the various figures. It is to beexpressly understood, however, that the drawings are for the purpose ofillustration and description only and are not intended as a definitionof the limits of the invention. As used in the specification and in theclaims, the singular form of “a”, “an”, and “the” include pluralreferents unless the context clearly dictates otherwise.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1-2 illustrate systems configured to use data-processing resourcescarried by a fleet of vehicles as a distributed data center to query thefleet of vehicles, in accordance with one or more embodiments.

FIG. 3 illustrates an exemplary interface to be used with a systemconfigured to use data-processing resources carried by a fleet ofvehicles as a distributed data center to query the fleet of vehicles, inaccordance with one or more embodiments.

FIG. 4A-4B illustrate a method to use data-processing resources carriedby a fleet of vehicles as a distributed data center to query the fleetof vehicles, in accordance with one or more embodiments.

DETAILED DESCRIPTION

FIG. 1 illustrates a system 100 configured to use data-processingresources carried by a fleet 12 of vehicles as a distributed data centerto query fleet 12 of vehicles. Fleet 12 may include a first vehicle 12a, a second vehicle 12 b, a third vehicle 12 c, and so forth. As usedhere, the term fleet may refer to a set of at least 5 vehicles, at least10 vehicles, at least 100 vehicles, at least 1000 vehicles, and/oranother number of vehicles. Individual vehicles may include a set ofresources for data processing and/or electronic storage, including butnot limited to persistent storage. Individual vehicles may include a setof sensors configured to generate output signals conveying informationrelated to the operation of the individual vehicles. System 100 mayinclude sets of resources 51, sets of sensors 52, a remote computingserver 40, electronic storage 119, and/or other components. In someimplementations, system 100 may be a distributed data center, include adistributed data center, or act as a distributed data center.

One or more components of system 100 may include one or more processors104 and/or other mechanisms/components for processing information. Forexample, a set of resources included in and/or carried by an individualvehicle may include one or more processors. For example, remotecomputing server 40 may include one or more processors. In someimplementations, other vehicle-specific components, such as, by way ofnon-limiting example, a vehicle event recorder, may include one or moreprocessors. In some implementations, some or all of the processors maybe configured via machine-readable instructions to perform variousfunctions. One or more components of system 100 may include electronicstorage 119 and/or other mechanisms/components for storing information.For example, a set of resources included in and/or carried by anindividual vehicle may include electronic storage. For example, remotecomputing server 40 may include electronic storage. In someimplementations, other vehicle-specific components, such as, by way ofnon-limiting example, a vehicle event recorder, may include electronicstorage.

By way of non-limiting example, as shown in FIG. 2 , individual sets ofresources 51 included in and/or carried by an individual vehicle (e.g.set of resources 51 c carried by vehicle 12 c) may include one or moreof electronic storage 70, a processor 71, a transceiver 72, an eventrecorder 73, and/or other components. First vehicle 12 a may carry afirst set of resources 51 a. Second vehicle 12 b may carry a second setof resources 51 b. Third vehicle 12 c may carry a third set of resources51 c, and so forth. Each set of resources may include instances of oneor more of electronic storage 70, a processor 71, a transceiver 72, anevent recorder 73, and/or other components. First set of resources 51 amay include a first transceiver. Second set of resources 51 b mayinclude a second transceiver, and so forth. For example, first set ofresources 51 a may include first electronic storage, second set ofresources 51 b may include second electronic storage, third set ofresources 51 c may include third electronic storage (e.g., storage 70),and so forth. For example, first set of resources 51 a may include oneor more processors, second set of resources 51 b may include one or moreprocessors, third set of resources 51 c may include one or moreprocessors (e.g., processor 71), and so forth.

Transceivers may be configured to transfer and/or receive information toand/or from other elements of system 100, including but not limited toother vehicles (or components carried by other vehicles in fleet 12),remote computing server 40, a user 60, a third party 61, and/or othercomponents. In some implementations, transceivers may be configured totransfer and/or receive information wirelessly, and/or otherwise provideinformation-distribution resources. For example, a transceiver may beconfigured to receive executable code, such as code that includes and/orrepresents a definition of a particular vehicle event, a particularmaneuver of a vehicle, and/or a particular condition of a vehicleoperator of a vehicle. In some implementations, transceivers may beconfigured to obtain, receive, measure, and/or otherwise determine oneor more conditions related to data transmissions. For example, one ormore current local data transmission conditions may include a currentbandwidth (e.g., in MB/s), a current transmission protocol (e.g., LTE,3G, 4G, 5G, Wi-Fi, etc.), a current transmission cost (e.g., in $/MB),and/or other conditions.

Referring to FIG. 1 , a set of sensors 52 may be configured to generateoutput signals conveying information. In some implementations, thegenerated information may be related to the operation of one or morevehicles in fleet 12. In some implementations, the generated informationmay be related to the surroundings of one or more vehicles in fleet 12.An individual set of sensors 52 may be carried by an individual vehicle.First vehicle 12 a may carry a first set of sensors 52 a. Second vehicle12 b may carry a second set of sensors 52 b. Third vehicle 12 c maycarry a third set of sensors 52 c, and so forth. The generatedinformation may include timing information, location information,operator information, and/or other information. In some implementations,generated information may be associated with timing information (e.g.,from a timer), location information, operator information, and/or otherinformation.

In some implementations, timing information may associate and/orotherwise relate the generated output signals with one or more momentsof generation by one or more particular sensors. For example, timinginformation may include time stamps that indicate moments of generation.For example, at a time labeled t₁ the speed of a vehicle may be 50 mph,at a time labeled t₂ the speed may be 55 mph, and so forth. A set oftime stamps or moments in time may form a timeline. In someimplementations, location information may associate and/or otherwiserelate the generated output signals with one or more locations ofgeneration (or, locations at the moment of generation) by one or moreparticular sensors. In some implementations, the operator informationmay associate and/or otherwise relate the generated output signals withindividual vehicle operators at the moments of generation. For example,a particular sensor may generate a particular output signal conveying aparticular operating parameter of an individual vehicle, such as speedand/or another operating parameter. The particular output signal mayinclude and/or be associated with a timestamp (e.g., time=t_(x)) thatindicates when the particular output signal was generated. For example,a series of output signals may be associated with a corresponding seriesof timestamps. In some implementations, the particular output signal maybe associated with a particular vehicle operator. For example, theparticular output signal may be associated with the particular vehicleoperator that was operating the individual vehicle at the time theparticular output signal was generated. In some implementations, a setof resources 51 may be configured to store generated information, timinginformation, location information, operator information, and/or otherinformation, e.g. in electronic storage. In some implementations,information may be stored after compression, filtering, and/or otherprocessing to reduce the required amount of storage space.

A sensor may be configured to generate output signals conveyinginformation related to the operation of a vehicle. Information relatedto the operation of a vehicle may include feedback information from oneor more of the mechanical systems of the vehicle, and/or otherinformation. In some implementations, at least one of the sensors may bea vehicle system sensor included in an engine control module (ECM)system or an electronic control module (ECM) system of the vehicle. Thesensors of a particular vehicle may be referred to as a set of sensors.An individual sensor is vehicle-specific.

Information related to current operating conditions of a vehicle mayinclude feedback information from one or more of the mechanical systemsof the vehicle, the electrical systems of the vehicle, and/or otherinformation. The mechanical systems of a vehicle may include, forexample, the engine, the drive train, the lighting systems (e.g.,headlights, brake lights), the braking system, the transmission, fueldelivery systems, and/or other mechanical systems. The mechanicalsystems of a vehicle may include one or more mechanical sensors,electronic sensors, and/or other sensors that generate the outputsignals (e.g., seat belt sensors, tire pressure sensors, etc.). In someimplementations, at least one of the sensors carried by a vehicle may bea vehicle system sensor included in an ECM system of the vehicle.

In some implementations, information related to current operatingconditions of a vehicle may include information related to theenvironment in and/or around the vehicle. The vehicle environment mayinclude spaces in and around an interior and an exterior of the vehicle.The information may include information related to movement of thevehicle, an orientation of the vehicle, a geographic position of thevehicle, a spatial position of the vehicle relative to other objects, atilt angle of the vehicle, an inclination/declination angle of thevehicle, and/or other information. In some implementations, the outputsignals conveying information may be generated via non-standardaftermarket sensors installed in the vehicle. Non-standard aftermarketsensors may include, for example, a video camera, a microphone, anaccelerometer, a gyroscope, a geolocation sensor (e.g., a GPS device), aradar detector, a magnetometer, radar (e.g. for measuring distance ofleading vehicle), and/or other sensors. In some implementations, the setof sensors carried by a vehicle may include multiple cameras positionedaround the vehicle and synchronized together to provide a 360-degreeview of the interior of the vehicle (e.g., the cabin) and/or a360-degree view of the exterior of the vehicle.

Although individual sets of sensors 52 a, 52 b, and 52 c are depicted inFIG. 1 as having three elements, this is not intended to be limiting.For individual vehicles, a set of sensors 142 may include one or moresensors located adjacent to and/or in communication with the variousmechanical systems of the vehicle, in one or more positions (e.g., at ornear the front of the vehicle, at or near the back of the vehicle, onthe side of the vehicle, on or near the windshield of the vehicle,facing outward and/or inward, etc.) to accurately acquire informationrepresenting the vehicle environment (e.g. visual information, spatialinformation, orientation information), and/or in other locations. Forexample, in some implementations, a set of sensors for a particularvehicle may be configured such that a first sensor is located near or incommunication with a rotating tire of the vehicle, and a second sensorlocated on top of the vehicle is in communication with a geolocationsatellite.

Individual sensors may be configured to generate output signalsconveying information. The information may include visual information,motion-related information, position-related information, biometricinformation, heat-related information, infra-red information, and/orother information. In some implementations, one or more components ofsystem 100 may determine one or more parameters that are measured,derived, estimated, approximated, and/or otherwise determined based onone or more output signals generated by one or more sensors.

Output signals generated by individual sensors (and/or information basedthereon) may be stored and/or transferred in electronic files. In someimplementations, output signals generated by individual sensors (and/orinformation based thereon) may be streamed to one or more othercomponents of system 100.

Individual sensors may include image sensors, cameras, and/or othersensors. Individual sensors may be configured to capture information,including but not limited to visual information, video information,audio information, heat information, geolocation information,orientation and/or motion information, depth information, and/or otherinformation. Information captured by one or more sensors may be marked,timestamped, annotated, and/or otherwise processed such that informationcaptured by other sensors can be synchronized, aligned, annotated,and/or otherwise associated therewith. For example, video informationcaptured by an image sensor may be synchronized with informationcaptured by an accelerometer, GPS unit, or other sensor. Output signalsgenerated by individual image sensors (and/or information based thereon)may be stored and/or transferred in electronic files.

System 100 may be coupled to individual vehicles. For example, system100 may be communicatively coupled to individual vehicles and/or tocomponents carried by individual vehicles, including but not limited totransceivers. For example, components of system 100 may be configured tocommunicate through one or more networks 121. The one or more networks121 may, by way of non-limiting example, include the internet.

Remote computing server 40 may include one or more processors 104.Remote computing server 40 may be remote, separate, and/or discrete fromthe fleet of vehicles 12. Remote computer server 40 may be physicallyunconnected to any vehicle in the fleet. One or more processors 104 maybe configured via machine-readable instructions 106 to perform variousfunctions. Remote computing server 40 may be configured to facilitatepresentation of a user interface to user 60 of remote computing server40 and/or third party 61. The user interface may be configured tofacilitate interaction between one or more users and remote computingserver 40. For example, the user interface may be configured to receiveuser input from user 60 and/or third party 61. In some implementations,the received input may represent executable code, which may include oneor more queries, definitions, and/or algorithms for particular vehicleevents, particular maneuvers of vehicles, and/or particular conditionsof vehicle operators. In some implementations, the received input mayrepresent a query, e.g. a distributed query. The query may be related toinformation stored on electronic storage, e.g. in multiple sets ofresources of multiple vehicles. Alternatively, and/or simultaneously, aquery may be related to one or more vehicle operators. Remote computingserver 40 may be further configured to transmit information (e.g.,executable code, and/or a query) to some vehicles in the fleet or to allvehicles of the fleet. Results and/or other responses from individualvehicles may be received, aggregated, and/or presented by remotecomputing server 40.

By way of non-limiting example, FIG. 3 illustrates a user interface 31to be used with system 100 to query fleet 12 of vehicles. By way ofnon-limiting example, user interface 31 may include a code area 32 usedto enter and/or select code elements that form executable code. Userinterface may include a launch code button 33 that, upon selection,facilitates distribution of the executable code in code area 32 to oneor more vehicles in a fleet. User interface 31 may include a firstresult area 34, a second result area 35, and/or other user interfaceelements. In some implementations, first result area 34 may be used topresent one or more results produced by execution of the executable codefrom code area 32. In some implementations, second result area 35 may beused to present one or more results produced by execution of alternativecode that is different from the executable code from code area 32. Forexample, first result area 34 and second result area 35 may be used by auser, a third party, and/or manual reviewer to support A/B testingbetween different algorithms to detect similar events, e.g. to determinealgorithm performance under controlled conditions (e.g., a defaultalgorithm to detect a fatigued driver and an alternative algorithm todetect a fatigued driver).

Referring to FIG. 2 , in some implementations, a set of resourcesincluded in and/or carried by an individual vehicle may include an eventrecorder (also referred to as vehicle event recorder). For example, setof resources 51 c carried by the vehicles may include event recorder 73,as shown in FIG. 2 . An event recorder may be configured to generate,detect, identify, capture, and/or record information related to theoperation of a vehicle. Information related to a vehicle may include, byway of non-limiting example, information related to and/or based onvehicle events. An event recorder may be configured to off-load and/orotherwise transmit information (e.g. through use of a transceiver suchas transceiver 72). In some implementations, an event recorder mayinclude one or more physical processors, electronic storage, and/orother components. In some implementations, an event recorder may detectvehicle events based on a comparison of the information conveyed by theoutput signals from one or more sensors to predetermined (variableand/or fixed) values, threshold, functions, and/or other information. Insome implementations, detections by the event recorder may be based, atleast in part, on information included in executable code and/or otherreceived information. An event recorder may identify vehicle events inreal-time or near real-time during operation of a vehicle.

In some implementations, system 100 may be configured to effectuatemanagement of distributed sets of resources 55. In some implementations,an individual distributed set of resources may include resources of thesame or similar type. For example, a first distributed set of resources55 a may include resources for electronic storage of information, asecond distributed set of resources 55 b may include resources thatprovide information-processing capabilities, a third distributed set ofresources 55 c may include resources that provideinformation-distribution capabilities, and so forth. For example, theresources for electronic storage of information may include a first datastore (included in first set of resources 51 a for the first vehicle), asecond data store (included in the second set of resources 51 b for thesecond vehicle), a third data store (included in the third set ofresources 51 c for the third vehicle), and so forth. For example, system100 may be configured to manage a distributed data store that includesdata stored in the first data store, the second data store, the thirddata store, and so forth. In some implementations, virtualizationcomponent 30 may be configured to effectuate management of differentlayers of virtualization of resources. For example, the lowest layer 90may include the physical resources, a next layer 91 may include thedistributed sets of resources, and another next layer 92 may includedistributed APIs, distributed applications, and/or services available tousers of remote computing server 40. The distributed API, application,and/or service layer may include support for different functions,services, and/or for different operating systems, e.g. through virtualmachines. In some implementations, virtualization component 40 may beconfigured to support different types of virtualization, including butnot limited to server virtualization, desktop virtualization,application virtualization, network virtualization, storagevirtualization, and/or other types of virtualization.

Referring to FIG. 1 , one or more processors 104 of remote computingserver 40 and/or of individual sets of resources 51 may be configured toexecute one or more computer program components. The computer programcomponents may include one or more of a presentation component 21, aninterface component 22, a distribution component 23, a code component24, a local result component 25, a centralized result component 26, aparameter determination component 27, a detection component 28, astorage component 29, a monetization component 30, and/or othercomponents.

Presentation component 21 may be configured to facilitate presentationof user interfaces, reports, and/or results to users, third parties,and/or vehicle operators. In some implementations, presentationcomponent 21 may facilitate presentation of a user interface to user 60of remote computing server 40. In some implementations, presentationcomponent 21 may facilitate presentation of a user interface to one ormore vehicle operators. In some implementations, presentation component21 may facilitate presentation of one or more reports, results, and/oruser interfaces to third party 61. This enables information to becommunicated between a vehicle operator and/or other components ofsystem 100. As an example, a warning regarding a dangerous drivingmaneuver and/or vehicle event may be displayed to the driver of thevehicle via such a user interface, e.g. as a notification. Presentationcomponent 21 enables information to be communicated between third party61, user 60, and/or other components of system 100.

Examples of interface devices suitable for inclusion in a user interfaceinclude a keypad, buttons, switches, a keyboard, knobs, levers, adisplay screen, a touch screen, speakers, a microphone, an indicatorlight, an audible alarm, a printer, a tactile feedback device, and/orother interface devices. It is to be understood that other communicationtechniques, either hard-wired or wireless, are also contemplated by thepresent disclosure as a user interface. Other exemplary input devicesand techniques adapted for use by users and/or vehicle operatorsinclude, but are not limited to, an RS-232 port, RF link, an IR link,modem (telephone, cable, and/or other modems), a cellular network, aWi-Fi network, a local area network, and/or other devices and/orsystems. In short, any technique for communicating information iscontemplated by the present disclosure as a user interface.

Interface component 22 may be configured to facilitate interaction withusers and/or vehicle operators. For example, a user may be a fleetmanager, or someone investigating fleet operations. Interface component22 may facilitate interaction through user interfaces. For example,interface component 22 may receive user input through a user interface.In some implementations, interface component 22 may receive user inputfrom user 60 of remote computing server 40. In some implementations,interface component 22 may receive user input from third party 61, e.g.via remote computing server 40. In some implementations, the receiveduser input may represent a distributed query, executable code, and/orother information. For example, an entire fleet of vehicles 12 (or anysubset thereof) may be queried for particular information. In someimplementations, a distributed query or other request may be associatedwith one or more response constraints. For example, distributioncomponent 23 may be configured to transmit the one or more responseconstraints to all or part of fleet of vehicles 12.

In some implementations, interface component 22 may be configured toeffectuate a review presentation to a user or reviewer, e.g. user 60. Areview presentation may be based on information related to one or moredetected vehicle events. In some implementations, a review presentationmay provide a prompt to a user or reviewer to provide manual reviewinput, e.g., regarding one or more detected vehicle events. For example,a reviewer may be prompted via a question, an inquiry, and/or via othertypes of prompts. For example, a reviewer may be asked whether a driverwas wearing a seatbelt at a particular point in time, or whether one ormore lanes appear to be closed. A review presentation may be implementedas a user interface to facilitate interaction for a reviewer. Forexample, such a user interface may receive review input from a reviewer,including but not limited to manual review input. In someimplementations, review input may be responsive to a prompt. In someimplementations, a vehicle operator may receive information based onreview input. Such information may be referred to as feedback. Forexample, a user interface for a vehicle operator (this may be referredto as a driver interface) may present a message to a vehicle operator to“remember to wear your seatbelt,” responsive to particular review inputreceived from a reviewer (through a different user interface). In someimplementations, a driver interface may be configured to detect avehicle operator's response and/or reaction to specific feedback. Insome implementations, the response and/or reaction by a vehicle operatormay be specific to the feedback received through the driver interface.In some implementations, review input may be used to update and/orchange a vehicle event report.

Distribution component 23 may be configured to transmit information fromremote computing server 40 to all or part of fleet of vehicles 12. Insome implementations, distribution component 23 may be configured totransmit information from remote computing server 40 to all or part ofthe transceivers that are included in and/or carried by fleet ofvehicles 12. In some implementations, transmission may be wireless. Insome implementations, transmission may be point-to-point. In someimplementations, transmission may be broadcast. In some implementations,transmission may be bi-directional. For example, distribution component23 may be configured to transmit executable code from remote computingserver 40 to individual vehicles in a fleet, e.g., based on the currentlocations of the individual vehicles. For example, distributioncomponent 23 may be configured to transmit query information from remotecomputing server 40 to some or all of the vehicles in fleet 12. In someimplementations, presentation component 21, interface component 22,and/or one or more other components of system 100 may be configured todetermine and/or present one or both of warnings and/or recommendationsto a vehicle operator, wherein the warnings and/or recommendations aredetermined based on detected vehicle events and/or other information.

Code component 24 may be configured to obtain executable code from user60, third party 61, and/or from a source external to system 100. In someimplementations, executable code may represent a query and/or analgorithm. In some implementations, executable code may include one ormore function calls to a standardized Application Program Interface orAPI. In some implementations, the standardized API may be stored inelectronic storage, including but not limited to electronic storage 119.The one or more function calls may be associated with functions thatoperate on information related to vehicles, including but not limited tothe operation of vehicles and/or the surroundings of vehicles. In someimplementations, the standardized API may include different subsets(e.g., different subsets of functions). System 100 may be configured tocontrol access by executable code to one or more particular subsets ofthe standardized API. For example, a first subset of functions of thestandardized API may be accessible to the executable code of aparticular third party, and a second subset of functions of thestandardized API may be inaccessible to the executable code of theparticular third party, at the same time. For example, the first subsetand the second subset may be mutually exclusive. In someimplementations, the executable code may include definitions and/oralgorithms for particular vehicle events, particular maneuvers ofvehicles, particular conditions of vehicle operators, and/or otherinformation. The extent of which subsets and/or which functions areaccessible and/or available may be controlled and/or limitedcontractually, e.g. as based on compensation paid by third party 61. Insome implementations, code component 24 may be configured to receiveexecutable code from user 60 and/or third party 61.

Local result component 25 may be configured to execute executable codelocally on one or more individual vehicles. For example, local resultcomponent 25 may be configured to execute executable code to produce aresult. In some implementations, produced result may be stored locallyper vehicle for future usage. Additionally, the set of resources on anindividual vehicle may be configured to transmit produced results toremote computing server 40. In some implementations, local resultcomponent 25 may be configured to execute executable code on previouslystored information for an individual vehicle, including but not limitedto previously detected vehicle events and/or other storedvehicle-specific information. Alternatively, and/or simultaneously, insome implementations, local result component 25 may be configured toexecute executable code over time and/or in an ongoing manner duringoperation of an individual vehicle. For example, the executable code mayinclude definitions and/or algorithms for new and/or improved vehicleevents which may be detected during operation of the individual vehicle,e.g., in real-time or near real-time. Occurrences of one or moredetected vehicle events may be stored locally and/or reported as soon aspossible (e.g., immediately subsequent to detection) and/or reported atpredefined times (e.g., once a week, or once a month). In other words,the detection of vehicle events based on information included inexecutable code may be backward-looking and/or forward-looking.

In some implementations, local result component 25 and/or an individualset of resources may be configured to execute the executable code in atesting environment. The testing environment may limit access of theexecutable code to a predefined subset of the individual set ofresources, such that elements of the individual set of resources thatare not within the predefined subset are protected from being accessedand/or corrupted. In some implementations, the testing environment maybe a so-called sandbox.

Centralized result component 26 may be configured to receive, aggregate,and/or otherwise process one or more results received from individualvehicles, including but not limited to results produced locally by localresult components of individual vehicles. In some implementations,centralized result component 26 may be located at remote computingserver 40.

Parameter determination component 27 may be configured to determinecurrent operating conditions and/or vehicle parameters. Parameterdetermination component 27 may determine current operating conditionsand/or vehicle parameters based on the information conveyed by theoutput signals from the sensors and/or other information. The one ormore current operating conditions may be related to the vehicle, theoperation of the vehicle, physical characteristics of the vehicle,and/or other information. In some implementations, parameterdetermination component 27 may be configured to determine one or more ofthe current operating conditions one or more times in an ongoing mannerduring operation of the vehicle.

In some implementations, operating conditions may include vehicleparameters. For example, vehicle parameters may be related to one ormore of an acceleration, a direction of travel, a turn diameter, avehicle speed, an engine speed (e.g. RPM), a duration of time, a closingdistance, a lane departure from an intended travelling lane of thevehicle, a following distance, physical characteristics of the vehicle(such as mass and/or number of axles, for example), a tilt angle of thevehicle, an inclination/declination angle of the vehicle, and/or otherparameters.

The physical characteristics of a vehicle may be physical features of avehicle set during manufacture of the vehicle, during loading of thevehicle, and/or at other times. For example, the one or more vehicleparameters may include a vehicle type (e.g., a car, a bus, a semi-truck,a tanker truck), a vehicle size (e.g., length), a vehicle weight (e.g.,including cargo and/or without cargo), a number of gears, a number ofaxles, a type of load carried by the vehicle (e.g., food items,livestock, construction materials, hazardous materials, an oversizedload, a liquid), vehicle trailer type, trailer length, trailer weight,trailer height, a number of axles, and/or other physical features.

In some implementations, parameter determination component 27 may beconfigured to determine one or more vehicle parameters based on theoutput signals from at least two different sensors. For example,parameter determination component 27 may determine one or more of thevehicle parameters based on output signals from a sensor related to theECM system and an external aftermarket added sensor. In someimplementations, a determination of one or more of the vehicleparameters based on output signals from at least two different sensorsmay be more accurate and/or precise than a determination based on theoutput signals from only one sensor. For example, on an icy surface,output signals from an accelerometer may not convey that a driver of thevehicle is applying the brakes of the vehicle. However, a sensor incommunication with the braking system of the vehicle would convey thatthe driver is applying the brakes. A value of a braking parameter may bedetermined based on the braking sensor information even though theoutput signals from the accelerometer may not convey that the driver isapplying the brakes.

Parameter determination component 27 may be configured to determinevehicle parameters that are not directly measurable by any of theavailable sensors. For example, an inclinometer may not be available tomeasure the road grade, but vehicle speed data as measured by a GPSsystem and/or by a wheel sensor ECM may be combined with accelerometerdata to determine the road grade. If an accelerometer measures a forcethat is consistent with braking, but the vehicle speed remains constant,the parameter component can determine that the measured force is acomponent of the gravity vector that is acting along the longitudinalaxis of the vehicle. By using trigonometry, the magnitude of the gravityvector component can be used to determine the road grade (e.g., pitchangle of the vehicle in respect to the horizontal plane).

In some implementations, one or more of the vehicle parameters may bedetermined one or more times in an ongoing manner during operation ofthe vehicle. In some implementations, one or more of the vehicleparameters may be determined at regular time intervals during operationof the vehicle. The timing of the vehicle parameter determinations(e.g., in an ongoing manner, at regular time intervals, etc.) may beprogrammed at manufacture, obtained responsive to user entry and/orselection of timing information via a user interface and/or a remotecomputing device, and/or may be determined in other ways. The timeintervals of parameter determination may be significantly less (e.g.more frequent) than the time intervals at which various sensormeasurements are available. In such cases, parameter determinationcomponent 27 may estimate vehicle parameters in between the actualmeasurements of the same vehicle parameters by the respective sensors,to the extent that the vehicle parameters are measurable. This may beestablished by means of a physical model that describes the behavior ofvarious vehicle parameters and their interdependency. For example, avehicle speed parameter may be estimated at a rate of 20 times persecond, although the underlying speed measurements are much lessfrequent (e.g., four times per second for ECM speed, one time per secondfor GPS speed). This may be accomplished by integrating vehicleacceleration, as measured by the accelerometer sensor where themeasurements are available 1000 times per second, across time todetermine change in speed that is accumulated over time again for themost recent vehicle speed measurement. The benefit of these morefrequent estimates of vehicle parameters are many and they includeimproved operation of other components of system 100, reduced complexityof downstream logic and system design (e.g., all vehicle parameters areupdated at the same interval, rather than being updating irregularly andat the interval of each respective sensor), and more pleasing (e.g.,“smooth”) presentation of vehicle event recorder data through a userinterface.

Detection component 28 may be configured to detect vehicle events. Insome implementations, vehicle events may be related to current operatingconditions of a vehicle. In some implementations, vehicle events may berelated to the surroundings of a vehicle. In some implementations,vehicle events may be related to the operator of a vehicle. For example,a vehicle event may be based on comparing one or more vehicle parameterswith one or more thresholds. In some implementations, detections may bebased on definitions and/or representations of vehicle events, actionsand/or conditions of vehicle operators, and/or vehicle maneuvers thatare included in executable code. For example, particular executable codefrom third party 61 may include a definition for the detection of anevent that represents an inattentive vehicle operator. Such executablecode may be distributed across a fleet of vehicles, and results from thedetection of an occurrence of the event that represents an inattentivevehicle operator may be transferred to remote computing server 40, andpresented to user 60 and/or third party 61.

For example, particular executable code from third party 61 may includea definition for the detection of an event that represents a fatiguedvehicle operator. Such executable code may be distributed across a fleetof vehicles, and results from the detection of an occurrence of theevent that represents a fatigued vehicle operator may be transferred toremote computing server 40, and presented to third party 61. Forexample, third party 61 may test and/or compare different algorithms todetect a fatigued vehicle operator. In some implementations, system 100may be configured to support A/B testing between different algorithms todetect similar events, e.g. to determine algorithm performance undercontrolled conditions. In some implementations, results from differentalgorithms (e.g., a default algorithm to detect a fatigued driver and analternative algorithm to detect a fatigued driver) may be presented toone or more manual reviewers, e.g. for head-to-head comparisons of oneor more results. In some implementations, presentation to reviewers(manual and/or otherwise) may be accomplished through user interfaces.For example, a manual reviewer may be able to enter feedback into a userinterface as part of a review.

For example, particular executable code from third party 61 may includea definition for the detection of an event that represents afuel-inefficient maneuver of a vehicle. Such executable code may bedistributed across a fleet of vehicles, and results from the detectionof an occurrence of the event that represents a fuel-inefficientmaneuver may be transferred to remote computing server 40, and presentedto third party 61.

In some implementations, detection component 28 may be configured todetect specific driving maneuvers based on one or more of a vehiclespeed, an engine load, a throttle level, an accelerator position,vehicle direction, a gravitational force, and/or other parameters beingsustained at or above threshold levels for pre-determined amounts oftime. In some implementations, an acceleration and/or force thresholdmay be scaled based on a length of time an acceleration and/or force ismaintained, and/or the particular speed the vehicle is travelling.Detection component 28 may be configured such that force maintained overa period of time at a particular vehicle speed may decrease a thresholdforce the longer that the force is maintained. Detection component 28may be configured such that, combined with engine load data, throttledata may be used to determine a risky event, a fuel wasting event,and/or other events.

Storage component 29 may be configured to store information inelectronic storage. For example, the information may be stored in theelectronic storage of a particular vehicle. In some implementations, thestored information may be related to detected vehicle events, determinedvehicle parameters, executable code, and/or other information. In someimplementations, storage component 29 may be configured to store vehicleevent records of detected vehicle events in electronic storage.

Monetization component 30 may be configured to exchange access byexecutable code to at least a part of the fleet for compensation. Forexample, the results from running executable code may be provided touser 60 and/or third party 61 in exchange for compensation.

In some implementations, one or more components of system 100 may beconfigured to obtain, receive, and/or determine contextual informationrelated to environmental conditions near and/or around vehicles.Environmental conditions may be related to weather conditions, roadsurface conditions, traffic conditions, visibility, and/or otherenvironmental conditions. In some implementations, environmentalconditions may be related to proximity of certain objects that arerelevant to driving, including but not limited to traffic signs,railroad crossings, time of day, ambient light conditions, altitude,and/or other objects relevant to driving. In some implementations,contextual information may include a likelihood of traffic congestionnear a particular vehicle, and/or near a particular location. In someimplementations, contextual information may include a likelihood of theroad surface near a particular vehicle and/or a particular locationbeing icy, wet, and/or otherwise potentially having an effect ofbraking. In some implementations, environmental conditions may includeinformation related to a particular driver and/or a particular trip. Forexample, with every passing hour that a particular driver drives hisvehicle during a particular trip, the likelihood of drowsiness mayincrease. In some implementations, the function between trip duration ordistance and likelihood of drowsiness may be driver-specific.

In some implementations, one or more environmental conditions may bereceived from one or more sources external to the vehicle. For example,a source external to the vehicle may include one or more externalproviders 18. For example, contextual information related to weatherconditions may be received from a particular external provider 18 thatprovides weather information. For example, contextual informationrelated to road surface conditions may be received from a particularexternal provider 18 that provides road condition information. Forexample, contextual information related to traffic conditions may bereceived from a particular external provider 18 that provides trafficinformation.

In some implementations, detection of vehicle events may further bebased one or more types of contextual information. In someimplementations, detection may be accomplished and/or performed at thevehicle. In some implementations, a value of a current operatingcondition that effectuates detection of a vehicle event and/ordetermination of an event type may vary as a function of the contextualinformation. For example, a speed of 50 mph (in a particulargeographical location) may not effectuate detection of a vehicle eventand/or determination of an event type when the road surface is dryand/or when traffic is light, but the same speed in the samegeographical location may effectuate detection of a vehicle event and/ordetermination of an event type responsive to contextual informationand/or other information indicating that the road surface is wet and/oricy (and/or may be wet and/or icy), or responsive to contextualinformation (and/or other information) that traffic is heavy (and/or maybe heavy). In this example, the contextual information (and/or otherinformation) may have an effect of the detection of vehicle eventsand/or the determination of event types. In some implementations,contextual information (and/or other information) may modify thesensitivity of the process and/or mechanism by which vehicle events aredetected and/or event types are determined. In some implementations,detection of vehicle events and/or determination of event types may bebased on one or more comparisons of the values of current operatingconditions with threshold values. In some implementations, a particularthreshold value may vary as a function of contextual information. Insome implementations, a particular threshold value may vary as afunction of other information, e.g. as determined based on sensoroutput.

By way of non-limiting example, lateral forces of about −0.3 g (e.g.,swerve left) and/or about +0.3 g (e.g., swerve right) may be a basisused to detect a swerve. In some implementations, the −0.3 g and/or +0.3g criteria may be used at the vehicle speeds less than about 10 kph. The−0.3 g and/or +0.3 g criteria may be scaled as the vehicle increases inspeed. In some implementations, the −0.3 g and/or +0.3 g criteria may bescaled (e.g., reduced) by about 0.0045 g per kph of speed over 10 kph.To prevent too much sensitivity, the lateral force criteria may belimited to about +/−0.12 g, regardless of the speed of the vehicle, forexample. In some implementations, the criterion for the given period oftime between swerves may be about 3 seconds.

Electronic storage 119 may comprise electronic storage media thatelectronically stores information. The electronic storage media ofelectronic storage 119 may comprise one or both of system storage thatis provided integrally (i.e., substantially non-removable) with system100 and/or removable storage that is removably connectable to system 100via, for example, a port (e.g., a USB port, a firewire port, etc.) or adrive (e.g., a disk drive, etc.). Electronic storage 119 may compriseone or more of optically readable storage media (e.g., optical disks,etc.), magnetically readable storage media (e.g., magnetic tape,magnetic hard drive, floppy drive, etc.), electrical charge-basedstorage media (e.g., EEPROM, RAM, etc.), solid-state storage media(e.g., flash drive, etc.), and/or other electronically readable storagemedia. Electronic storage 119 may store software algorithms, recordedvideo event data, information determined by processor 104, informationreceived via a user interface, and/or other information that enablessystem 100 to function properly. Electronic storage 119 may be (in wholeor in part) a separate component within system 100, or electronicstorage 119 may be provided (in whole or in part) integrally with one ormore other components of system 100.

As described above, processor 104 may be configured to provideinformation-processing capabilities in system 100. As such, processor104 may comprise one or more of a digital processor, an analogprocessor, a digital circuit designed to process information, an analogcircuit designed to process information, a state machine, and/or othermechanisms for electronically processing information. Although processor104 is shown in FIG. 1 as a single entity, this is for illustrativepurposes only. In some implementations, processor 104 may comprise aplurality of processing units. These processing units may be physicallylocated within the same device (e.g., a vehicle event recorder), orprocessor 104 may represent processing functionality of a plurality ofdevices operating in coordination.

Processor 110 may be configured to execute components 21-30 by software;hardware; firmware; some combination of software, hardware, and/orfirmware; and/or other mechanisms for configuring processingcapabilities on processor 110. It should be appreciated that althoughcomponents 21-30 are illustrated in FIG. 1 as being co-located within asingle processing unit, in implementations in which processor 104comprises multiple processing units, one or more of components 21-30 maybe located remotely from the other components. The description of thefunctionality provided by the different components 21-30 describedherein is for illustrative purposes, and is not intended to be limiting,as any of components 21-30 may provide more or less functionality thanis described. For example, one or more of components 21-30 may beeliminated, and some or all of its functionality may be provided byother components 21-30. As another example, processor 104 may beconfigured to execute one or more additional components that may performsome or all of the functionality attributed below to one of components21-30.

FIGS. 4A-4B illustrate a method 1000 to use a distributed data center toquery a fleet of vehicles. The operations of method 1000 presented beloware intended to be illustrative. In some implementations, method 1000may be accomplished with one or more additional operations notdescribed, and/or without one or more of the operations discussed.Additionally, the order in which the operations of method 1000 areillustrated (in FIGS. 4A-4B) and described below is not intended to belimiting. In some implementations, two or more of the operations mayoccur substantially simultaneously.

In some implementations, method 1000 may be implemented in one or moreprocessing devices (e.g., a digital processor, an analog processor, adigital circuit designed to process information, an analog circuitdesigned to process information, a state machine, and/or othermechanisms for electronically processing information). The one or moreprocessing devices may include one or more devices executing some or allof the operations of method 1000 in response to instructions storedelectronically on one or more electronic storage mediums. The one ormore processing devices may include one or more devices configuredthrough hardware, firmware, and/or software to be specifically designedfor execution of one or more of the operations of method 1000.

Referring to FIGS. 4A-4B and method 1000, at an operation 1002, outputsignals are generated by a first set of sensors carried by a firstvehicle, wherein the output signals convey first information related tooperation of the first vehicle. In some embodiments, operation 1002 isperformed by a set of sensors the same as or similar to set of sensors52 a (shown in FIG. 1 and described herein).

At an operation 1004, vehicle-specific information is determined andstored locally on the first vehicle. The stored vehicle-specificinformation is based on the first information. In some embodiments,operation 1004 is performed by a set of resources the same as or similarto set of resources 51 a (shown in FIG. 1 and described herein).

At an operation 1006, executable code is obtained by the remotecomputing server from a user. The executable code includes one or morefunction calls to a standardized Application Program Interface (API).The one or more function calls operate on information related tooperation of vehicles. In some embodiments, operation 1006 is performedby a code component the same as or similar to code component 24 (shownin FIG. 1 and described herein).

At an operation 1008, the executable code is transmitted by the remotecomputing server to a set of transceivers carried by the fleet ofvehicles. The set of transceivers includes a first transceiver of thefirst vehicle. In some embodiments, operation 1008 is performed by adistribution component the same as or similar to distribution component23 (shown in FIG. 1 and described herein).

At an operation 1010, the executable code is received at the firstvehicle from the remote computing server. In some embodiments, operation1010 is performed by a set of resources the same as or similar to set ofresources 51 a (shown in FIG. 1 and described herein).

At an operation 1012, the executable code is executed at the firstvehicle to produce a first result. In some embodiments, operation 1012is performed by a local result component the same as or similar to localresult component 25 (shown in FIG. 1 and described herein).

At an operation 1014, the first result is transferred by the firsttransceiver to the remote computing server. In some embodiments,operation 1014 is performed by a set of resources the same as or similarto set of resources 51 a (shown in FIG. 1 and described herein).

At an operation 1016, a set of results is received by the remotecomputing server from the set of receivers. The set of results includesthe first result. In some embodiments, operation 1016 is performed by acentralized result component the same as or similar to centralizedresult component 26 (shown in FIG. 1 and described herein).

At an operation 1018, a presentation is facilitated, wherein thepresentation is based on the first result to the third party. In someembodiments, operation 1018 is performed by a presentation component thesame as or similar to presentation component 21 (shown in FIG. 1 anddescribed herein).

Although the system(s) and/or method(s) of this disclosure have beendescribed in detail for the purpose of illustration based on what iscurrently considered to be the most practical and preferredimplementations, it is to be understood that such detail is solely forthat purpose and that the disclosure is not limited to the disclosedimplementations, but, on the contrary, is intended to covermodifications and equivalent arrangements that are within the spirit andscope of the appended claims. For example, it is to be understood thatthe present disclosure contemplates that, to the extent possible, one ormore features of any implementation can be combined with one or morefeatures of any other implementation.

What is claimed is:
 1. A system configured to query vehicle eventinformation for a fleet of vehicles, the system configured to couplewith the fleet of vehicles, wherein the fleet includes a first vehicle,the system comprising: a remote storage server including one or moreparticular processors, wherein the remote storage server is separate anddiscrete from the fleet of vehicles, wherein the remote storage serveris configured to electronically store information, wherein theinformation includes vehicle-specific information received from thefleet of vehicles; and a remote computing server including one or moreprocessors, wherein the remote computing server is separate and discretefrom the fleet of vehicles, and wherein the one or more processors areconfigured via machine-readable instructions to: obtain, at the remotecomputing server, executable code from a user, wherein the executablecode includes one or more function calls to a standardized ApplicationProgram Interface (API), wherein the one or more function calls operateon the vehicle-specific information that has previously been stored atthe remote storage server, and wherein the executable code includes adefinition of one or more of (i) a particular vehicle event, (ii) aparticular maneuver of a vehicle, (iii) a particular condition of avehicle operator of a vehicle, and/or (iv) a particular environmentalcondition pertaining to an environment outside of a vehicle; andtransmit the executable code to the remote storage server for execution;wherein the one or more particular processors of the remote storageserver are further configured to: subsequent to receipt of theexecutable code from the remote computing server, execute the executablecode to produce a first result, wherein the first result is based on thevehicle-specific information; transfer information based on the firstresult to the remote computing server; and wherein the one or moreprocessors of the remote computing server are further configured to:obtain the first result; and facilitate a presentation based on thefirst result to the user.
 2. The system of claim 1, wherein theparticular environmental condition pertains to weather conditions. 3.The system of claim 1, wherein the particular environmental conditionpertains to traffic conditions.
 4. The system of claim 1, wherein theparticular environmental condition pertains to visibility.
 5. The systemof claim 1, wherein the particular environmental condition pertains toroad surface conditions.
 6. The system of claim 1, wherein theparticular environmental condition pertains to certain objects inproximity to the first vehicle.
 7. The system of claim 1, wherein theone or more processors are further configured to enable an operator ofthe remote computing server to control access by the executable code tothe standardized Application Program Interface (API) such that a firstsubset of the standardized API is not accessible to the executable codeand a second subset of the standardized API is accessible to theexecutable code, and wherein control of the access by the executablecode to the standardized Application Program Interface (API) includes anability to modify elements of the first and/or second subset of thestandardized API.
 8. The system of claim 1, wherein the first result isbased on the definition included in the executable code.
 9. The systemof claim 8, wherein the first result includes video information based onimage information captured by a vehicle-specific image sensor.
 10. Amethod for querying vehicle event information for a fleet of vehicles,wherein the distributed data center includes a remote computing serverand a remote storage server, wherein the fleet includes a first vehicle,the method comprising: electronically storing information, by the remotestorage server that is separate and discrete from the fleet of vehicles,wherein the information includes vehicle-specific information receivedfrom the fleet of vehicles; obtaining, by the remote computing server,executable code from a user, wherein the executable code includes one ormore function calls to a standardized Application Program Interface(API), wherein the one or more function calls operate on thevehicle-specific information that has previously been stored at theremote storage server, and wherein the executable code includes adefinition of one or more of (i) a particular vehicle event, (ii) aparticular maneuver of a vehicle, (iii) a particular condition of avehicle operator of a vehicle, and/or (iv) a particular environmentalcondition pertaining to an environment outside of a vehicle;transmitting, by the remote computing server, the executable code to theremote storage server for execution; executing, by the remote storageserver, the executable code to produce a first result, wherein the firstresult is based on the vehicle-specific information; transferring, bythe remote storage server, information based on the first result to theremote computing server; obtaining, by the remote computing server, thefirst result; and facilitating a presentation based on the first resultto the user.
 11. The method of claim 10, wherein the particularenvironmental condition pertains to weather conditions.
 12. The methodof claim 10, wherein the particular environmental condition pertains totraffic conditions.
 13. The method of claim 10, wherein the particularenvironmental condition pertains to visibility.
 14. The method of claim10, wherein the particular environmental condition pertains to roadsurface conditions.
 15. The method of claim 10, further comprising:enabling an operator of the remote computing server to control access bythe executable code to the standardized Application Program Interface(API) such that a first subset of the standardized API is not accessibleto the executable code and a second subset of the standardized API isaccessible to the executable code, and wherein control of the access bythe executable code to the standardized Application Program Interface(API) includes an ability to modify elements of the first and/or secondsubset of the standardized API.
 16. The method of claim 10, wherein thefirst result is based on the definition included in the executable code.17. The method of claim 16, wherein the first result includes videoinformation based on captured image information captured by avehicle-specific image sensor.